[Microsoft.Management] Add listDescendants, listMembers, and reshape listAncestors on serviceGroups (2026-03-01-preview) - #44769
Conversation
…6-03-01-preview) Adds a tenant-scoped POST action that returns the descendant service groups of a service group, ordered by hierarchy. Response reuses ServiceGroupCollectionResponse (Azure.Core.Page<ServiceGroup>) so clients get the full ServiceGroup resource per descendant. Supports skipToken-based pagination.
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
Comment generated by After APIView workflow run. |
|
Thanks for the update. One blocking check is still failing on the current head: Swagger LintDiff - Analyze Code. Could you please share/fix the exact LintDiff error from that run and push a fix (or re-run if this was transient)? We can continue ARM sign-off once this is green. |
…nts-2026-03-01-preview
|
Hi kanikasp113, two things needed before this can merge:
All ARM review items are resolved and suppression review is approved - the PR is ready from the ARM side once the above are addressed. |
TypeSpec suppressions requiring review (testing, non-blocking)Status: ❌ Approval required (currently under testing, review NOT enforced) — 4 suppressions
New suppressions (4)
For an overview of TypeSpec linting rules click here. 💬 Have feedback on the TypeSpec suppression flow? Let us know. |
|
kanikasp113 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
…nts-2026-03-01-preview
- Renamed 'properties' -> 'relationshipProperties' (non-SG entries only) - Moved parent to top level as 'serviceGroupParent' (plain SG arm-id) - Removed wrapper types DescendantServiceGroupProperties, DescendantServiceGroupParent, ServiceGroupMemberParent
…nts-2026-03-01-preview
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
listDescendantsaction to Microsoft.Management/serviceGroups under the 2026-03-01-preview API version.Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.